Please move the changelog entry to v1. Can you verify that the forecasting job page correctly opens in rq-dashboard to show the job kwargs?

Done, I moved the changelog entry to the v1 section.

I also verified that the forecasting job page opens correctly in rq-dashboard and shows the job kwargs:

The most recent job in the screenshot was created from this branch. The earlier jobs were created from main.

Main differences:

• On main, the queued job calls the bound run_cycle(...) method directly.

• On this branch, the queued job calls the module-level run_train_predict_cycle_job(...).

• On main, most values are passed as flat kwargs to run_cycle(...), including ORM-backed objects like sensor=<Sensor ...> and sensor_to_save=<Sensor ...>.

• On this branch, the kwargs are grouped into a safer structure:

  • config: model/config values, with regressors represented as future_regressor_ids / past_regressor_ids
  • parameters: forecast parameters, with sensors represented as sensor_id / sensor_to_save_id
  • data_source_id: the saved forecasting data source
  • cycle timing kwargs: train_start, train_end, predict_start, predict_end, counter, multiplier

So the same forecasting information is still visible in rq-dashboard, but ORM objects are replaced by IDs and grouped under config / parameters.

The image is of the rq-dashboard jobs (plural) page. Can you click on the job ID to open the job (singular) page?

The image is of the rq-dashboard jobs (plural) page. Can you click on the job ID to open the job (singular) page?

• Main:

This PR:

I made some follow-up commits to make the queued payload handling less brittle.

The serializer now preserves plain config/parameter fields by default, and only replaces ORM-backed fields with IDs (future_regressors / past_regressors, sensor / sensor_to_save). I also added a guard so any remaining ORM object in the final queued job payload fails before enqueueing, instead of being pickled into Redis.

Added tests for:

• plain config/parameter fields surviving serialization
• regressors and sensors being converted to IDs and restored in the worker session
• unexpected ORM objects failing loudly

and added some docstrings and comments